To define publishing servers
1. In the Maintenance area of Content Management, select Publishing servers.
2. Select an existing publishing server to change its properties, or you can add or delete a publishing server.
To verify/change a publishing service code
If you need to verify or change the Publishing Server Code assigned to an installed publishing service,
1. Open the PublishService.exe.config file in a text editor on the appserver or external web server.
Default location: C:\Program Files\ASI\iMIS\Net\bin
2. In the <SystemParams> declaration, verify or change the value of the PublishServerCode key. The value must be a single uppercase letter from A to Z, and must be unique among all publishing services used by a given instance (database) of iMIS.
To manually define additional publishing servers
The iMIS installer automatically defines a corresponding publishing server for the default instance of the publishing service installed by iMIS. However, in some WCM installation scenarios, you are instructed to manually install one or more additional instances of the publishing service at a command line.
1. Manually create a single corresponding publishing server for every publishing service that you have manually installed.
2. When you add a new publishing server, review the Publish on Servers property for all existing content folders to specify whether the rendered files from content records in those folders should be made available to the iMIS sites that are associated with these manually-created publishing servers.
To define sets of publishing service codes
When you install WCM on a web server (or install an additional publishing service for each manually created IIS application or IIS web site), you are prompted to specify a Publishing Server Code to uniquely identify the publishing service that is created during installation (it always defaults to the value A). When you define a publishing server in the WCM environment to control the behavior of a specific publishing service, you use this code to link the publishing service to its corresponding publishing server.
The Publishing Server Code must be unique among all publishing services used by a given instance of iMIS. For example, your production iMIS server might use the code A to identify its instance of the publishing service, and you might also have 3 other external web servers located in different geographic locations whose Publishing Server Codes might be B, C, and D, respectively.
Tip: You can duplicate codes across test and production instances, since they're still unique within their specific databases.
Caution! The publishing server associated with the base iMIS installation must always be defined as the one and only Default (the one PublishServerRef row set with the IsDefault flag). Unless this one instance is set as the default, the Multi-Instance Utility will not work as expected.
Troubleshooting
■ You must be a member of at least one Master Admin content authority group (CAG).
■ You must already have installed WCM on one or more web servers and noted the Publish Server Code that you specified to use for the iMIS publishing service that was installed during that process.
■ Note: You must associate no more than one publishing server with each publishing service. If your environment has more than one IIS application or IIS web site that is hosting iMIS sites on a given server, you must install one publishing service for each such IIS application and IIS web site, and you must define a single corresponding publishing server for each publishing service. See Installing WCM on web servers.
Note: Membership in the SysAdmin security role effectively grants the full set of Document System permissions and the full set of CAG permissions (you are effectively a member of a MasterAdmin CAG too). However, to participate in web content authoring workflow, even members of the SysAdmin role must be an explicitly-listed member of at least one CAG.